Secure DNS query

ABSTRACT

A secure DNS query may be made by establishing a secure connection with a specific DNS server to determine an address for a hostname. A client device may have a database that may contain a record of a secure DNS server for one or more hostnames. When a DNS request contains one of the specified hostnames, an authenticated session may be created with the designated secure DNS server and a network address for the hostname is returned using the session. The authenticated session may authenticate a client device to the server as well as authenticate the server to the client. In some embodiments, the secure DNS server may accept connections from authenticated clients and may disregard connection requests from non authenticated clients.

BACKGROUND

Domain Name Service (DNS) is a technology used within various networks, including the Internet, to resolve a text based hostname, such as www.example.com to an Internet Protocol (IP) address such as 208.77.188.166. Many applications, such as web browsers, may use the DNS service to resolve names when making various queries or establishing connections across a network. In many private networks, such as a company or home intranet, a DNS service may service DNS requests within the network and, when a query fails within the local network, a query may roll over to an Internet or wide area network DNS service.

SUMMARY

A secure DNS query may be made by establishing a secure connection with a specific DNS server to determine an address for a hostname. A client device may have a database that may contain a record of a secure DNS server for one or more hostnames. When a DNS request contains one of the specified hostnames, an authenticated session may be created with the designated secure DNS server and a network address for the hostname is returned using the session. The authenticated session may authenticate a client device to the server as well as authenticate the server to the client. In some embodiments, the secure DNS server may accept connections from authenticated clients and may disregard connection requests from non authenticated clients.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings,

FIG. 1 is a diagram illustration of an embodiment showing a network with a secure DNS sever.

FIG. 2 is a flowchart illustration of an embodiment showing a method for communicating with a secure DNS server by a client.

FIG. 3 is a flowchart illustration of an embodiment showing a method for operations of a secure DNS server when processing a secure DNS request from a client.

DETAILED DESCRIPTION

A secure domain name system (DNS) server may be queried for a list of predefined hostnames. The secure DNS server may be accessed by a predefined network address from a client device, and mutual authentication or other security measures may be used to verify that a DNS query with the secure DNS server is authentic and accurate.

A secure DNS server may be used to thwart various ‘man in the middle’ attacks where a client's DNS query may be intercepted and the client may be redirected to a malicious server in place of a desired server. Such a system may also be used to avoid corrupt records in public or shared DNS servers.

A secure DNS server may be used for giving access to hosts that are not available through a public DNS call. For example, a corporate network may have several access points that may be used by employees or by customers. Such access points may be made available through a secure DNS server that may return addresses for hostnames that are not available through a public DNS system.

A client device may include a table or other database that contains hostnames that may be queried using a secure DNS server. When a hostname is presented to the client DNS query engine, a secure connection may be made to the secure DNS server to obtain an authenticated and reliable network address for the hostname. If a hostname is presented that is not contained in the database, a non-secure DNS query may be made. The hostnames in the database may be a predefined list of hostnames that may be, for example, to secure sites or other sites where a misdirected DNS query may be a security concern.

Throughout this specification, like reference numbers signify the same elements throughout the description of the figures.

When elements are referred to as being “connected” or “coupled,” the elements can be directly connected or coupled together or one or more intervening elements may also be present. In contrast, when elements are referred to as being “directly connected” or “directly coupled,” there are no intervening elements present.

The subject matter may be embodied as devices, systems, methods, and/or computer program products. Accordingly, some or all of the subject matter may be embodied in hardware and/or in software (including firmware, resident software, micro-code, state machines, gate arrays, etc.) Furthermore, the subject matter may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media.

Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by an instruction execution system. Note that the computer-usable or computer-readable medium could be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, of otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.

When the subject matter is embodied in the general context of computer-executable instructions, the embodiment may comprise program modules, executed by one or more systems, computers, or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.

FIG. 1 is a diagram of an embodiment 100 showing a network with a secure DNS server. Embodiment 100 is a simplified example used to highlight various characteristics, features, and uses of a secure DNS server.

The diagram of FIG. 1 illustrates functional components of a system and may not correspond directly with a hardware or software component of a system. In some cases, a component may be a hardware component, a software component, or a combination of hardware and software. Hardware components may include general purpose components adaptable to perform many different tasks or specially designed components that may be optimized to perform a very specific function. Some of the components may be application level software, while other components may be operating system level components. In some cases, the connection of one component to another may be a close connection where two or more components are operating on a single hardware platform. In other cases, the connections may be made over network connections spanning long distances. Each embodiment may use different hardware, software, and interconnection architectures to achieve the various functions described.

Embodiment 100 is an example of a system that includes a secure DNS server. The secure DNS server may be used to respond to DNS queries for a set of hostnames that is contained on a client device. Requests for network addresses for other hostnames may be handled using a non-secure DNS server.

Requests that are routed to a secure DNS server may be authenticated and may be performed using various security mechanisms. In many cases, the client may authenticate itself to the server and the server may authenticate itself to the client. In some cases, a secure session may be established using various secure protocols including Internet Protocol Security (IPsec), Secure Sockets Layer (SSL), or some other secure protocol. Transmissions within the secure session may additionally be encrypted.

A client 102 may be connected to the Internet 104 or other network, including a local area network or a wide area network. The client 102 may have a secure name resolver 107 that may resolve a hostname address for a given hostname using a secure DNS server 110 in some cases. An example of the operation of a secure name resolver is given in embodiment 200 contained in this specification. Similarly, the client 102 may have an unsecure name resolver 109 that may resolve hostname addresses using an unsecure DNS server 118.

The client 102 may have a hostname policy database 106 that may contain a set of hostnames and an address or other identifier such as a hostname of a secure DNS server 110. The database 106 may be queried for each DNS query to determine if a requested hostname corresponds to a secure DNS server. When a requested hostname does correspond with a secure DNS server, a connection is established with the secure DNS server 110 for the query.

In many cases, a connection between the client 102 and the secure DNS server 110 may be established after the client 102 transmits an identifier 108 to the secure DNS server 110. The identifier 108 may be used to authenticate the client 102 to the secure DNS server 110. The secure DNS server 110 may contain a security mechanism 113 that may provide various authentication, encryption, and security mechanisms for communicating with the client 102. The secure DNS server 110 may include a secure name resolver 115 that may be the operational portion of the secure DNS server 110 that processes hostname address requests from a client 102 in a secure and/or authenticated manner. An example of the operations of a secure name resolver 115 is illustrated in FIG. 3.

During an initial transmission to establish a connection with the secure DNS server 110, the client 102 may transmit an identifier 108. In many cases, the identifier 108 may include an IP address in an initial communications packet. The IP address may be screened by the secure DNS server 110 to determine if the client IP address is permitted to access the secure DNS server 110.

During subsequent communications, the client 102 may transmit other forms of an identifier 108 to authenticate the client 102 to the secure DNS server 110. For example, the client 102 may transmit a Media Access Control (MAC) address, a hardware serial number such as a processor serial number, or use other hardware identifiers. Other examples may include transmitting a serial number that may be stored in a hardware dongle, access card, or some other identifier.

In some cases, a user-level identifier 108 may be transmitted to the secure DNS server 110. A user-level identifier 108 may be an identifier such as a user name, verification from a fingerprint reader, an authenticated voice print, retina scan, or output from other types of physiological reading devices.

The identifier 108 may be used by the secure DNS server 110 during various stages of a session to determine that the client 102 is authenticated and permitted to perform a DNS query.

The secure DNS server 110 may have a client database 114 and a DNS database 112. The client database 114 may contain identifiers for various client devices to compare to the authentication identifier 108 that may be transmitted by the client 102. In many cases, the client database 114 may contain IP addresses or ranges of addresses that may be permitted to establish secure sessions with the secure DNS server 110. In many embodiments, the secure DNS server 110 may reject or ignore communication requests from devices that have IP addresses outside of a predefined range of devices.

The DNS database 112 may contain records that match hostnames with IP or network addresses for various hosts. In many embodiments, the secure DNS server 110 may be used to provide DNS services for a small number of hosts.

In an example, a company may have a group of servers that may be used for secure sessions by employees. Each employee may access the company servers by first establishing a connection with the secure DNS server 110, authenticating with the secure DNS server 110, and receiving a network address for a company server, which may be a trusted server 116. After receiving the network address to the company server, each client may establish a connection with the company server.

In many embodiments, a connection established with an address received from a secure DNS server 110 may be a secure connection. In a typical use scenario, the hostnames requested from the secure DNS server 110 may be hostnames for connections that are security sensitive. As such, the subsequent connections with the hosts may be secure connections.

In some embodiments, the secure DNS server 110 may provide network addresses for a small list of hostnames. For example, a secure DNS server may be used for address resolution for employees of a company who wish the access a secure access point for a company network. In such a case, the secure DNS server may contain only one record of a hostname to network address map.

In other embodiments, the secure DNS server 110 may provide a secure DNS service for a large number of hostnames. In such cases, the secure DNS server 110 may be used to provide an authenticated, accurate, and in some cases a guaranteed DNS service that may provide secure DNS services to any client device. Such a case may enable the general public to establish a secure connection with a secure DNS server and receive address information to avoid ‘man in the middle’ attacks. Such an attack may be where a network interloper may intercept an outgoing or returning DNS query and respond with an address that directs the client to a malicious or undesired server rather than an intended server.

In some such embodiments, the secure DNS server 110 may be used to avoid DNS queries to various unsecure DNS servers 118 that may contain corrupt or incorrect records in the DNS database 120. When a corrupt record enters the DNS system, the record may propagate through various caches and servers for a considerable amount of time before the record is expunged or overwritten. When the secure DNS server 110 is used for large numbers of DNS queries, the secure DNS server 110 may be populated with authenticated or verified DNS records.

In embodiments where the secure DNS server 110 is used for large numbers of DNS records, the secure DNS server 110 may provide authentication to the client 102 but the client 102 may not provide authentication to the secure DNS server 110. In such an embodiment, the secure DNS server 110 may establish a connection using IPsec, SSL, or other secure technologies. Some such technologies may allow for one way authentication from the server to the client but may not enforce authentication from the client to the server.

When a client 102 accesses the secure DNS server 110, an authentication may be recorded for the requesting device. Such a record may be made in the client database 114 and used to audit the connection requests for specific hostnames. In some embodiments, a database of authenticated clients may be kept and used for security analysis or other recordkeeping.

In cases where the client 102 makes a request for an address using a hostname that is not in the hostname policy database 106, the client 102 may make a DNS request from the unsecure DNS server 118. The DNS server 118 may have a DNS database 120 that may contain multitudes of DNS entries for large numbers of hostnames across the network, including the Internet. In general, the DNS server 118 may direct a client 102 to a non-trusted server 122 by responding to a request for an address when given a hostname associated with the server 122.

In many embodiments, the client 102 may attempt to obtain a network address by accessing the hostname policy database 106 first, and if an entry is found, making a connection to a secure DNS server 110. If no entry is found, a query may be made to an unsecure DNS server 118. In many such embodiments, when an entry is found in the hostname policy database 106 and the connection fails for some reason, the client 102 may be prevented from making the same query of the unsecure DNS server 118.

FIG. 2 is a flowchart illustration of an embodiment 200 showing a client method for communicating with a secure DNS server. The embodiment 200 illustrates a simplified example of actions performed by a client and may illustrate some of the steps that may be performed in order to engage a secure DNS server and receive a network address that corresponds to a hostname. Other embodiments may use different terminology or nomenclature and may include additional steps or may combine two or more steps into a single step. In other embodiments, some steps illustrated as serial may be performed in parallel and vice versa.

Embodiment 200 is an example of a method for communicating with a secure DNS server, which may include secure name resolver steps 201 and unsecure name resolver steps 205 that may correspond with the secure name resolver 107 and unsecure name resolver 109 in FIG. 1.

In the method of embodiment 200, a request for a hostname address is received in block 202 and if the hostname is found in a hostname policy database in block 204, the process continues to perform a request with a secure DNS server. If the hostname is not found in a hostname policy database in block 204, an unsecured DNS request may be performed.

In many embodiments, a client device may check an incoming DNS request against a hostname policy database to determine if the hostname is associated with a secure DNS server or not. When the hostname is found in the hostname policy database, the client may proceed with a secure DNS connection.

In many embodiments, once the client begins a secure DNS connection, it may be prevented from rolling over to an unsecure DNS request. In such a situation, a failure with a secure DNS request may result in a failed DNS request and the client's subsequent connection to a requested host may not be completed. This logic may be applied when a ‘man in the middle’ attack may be suspected and an unsecure DNS request may make the client vulnerable.

An unsecured DNS request may be performed by sending the request to an unsecured DNS server in block 206, a hostname address may be received in block 208, and a connection may be established using the hostname address in block 210. In many cases, communications with unsecured DNS servers may be made using User Datagram Protocol or UDP. UDP is a low-overhead communication protocol that may transmit short messages across a network in a relatively unsecure manner. UDP is generally more efficient than other, more complex protocols.

The unsecured DNS request may be vulnerable to ‘man in the middle’ attacks where one or more portions of the unsecure DNS request may be intercepted and changed by a malicious network interloper. When an unsecure DNS request is changed, a client may be redirected to a malicious host rather than an intended host without realizing that the redirection has happened.

For example, a ‘man in the middle’ attack may be performed when a user on a client device attempts to access the user's bank account using a web browser. A DNS request may be generated by the web browser, and the request may include the hostname for the user's bank. A malicious interloper may identify the DNS request for the bank and send a response to the client device for a false website that appears similar to the bank's website. The unsuspecting user may be tricked into giving account information, user identification, passwords, or other sensitive information to the false website. Such information may be used by the interloper for accessing the bank's website without the user's knowledge.

The ‘man in the middle’ attack may occur at different stages of the DNS query. In a first type of attack, a DNS request may be redirected to a false or malicious DNS server that responds with an improper address for a hostname. In this type of attack, the interloper may intercept a DNS request being sent from the client to the DNS server.

In a second type of attack, an interloper may intercept the return message from a DNS server to the client and may change the contents of the return message to redirect a client device to a malicious host. In a variation of the second type of attack, an interloper may surreptitiously change the client's outgoing message to request an address for a different hostname from the DNS server.

In the first type of attack, the client device may unknowingly communicate with a malicious DNS server. In the second type of attack, the client may communicate with a proper DNS server but the communication between the client and DNS server may be intercepted and changed.

A secure DNS query may help to thwart the first type of ‘man in the middle’ attack by authenticating the DNS server to the client so that the client is assured that the DNS server is indeed the proper server. Additionally, the second type of attack may be thwarted when a secure connection may be established between the client and DNS server.

In some embodiments, a secure DNS server may be used to dispense addresses for hostnames that are not publicly available through unsecured DNS servers. An example may be a corporate network that may make some access points available to limited groups of people, such as customers or employees. Such access points may be available through a secure DNS server that contains DNS records that may not be found in public DNS records.

A secure DNS request may be processed by looking up a secure DNS server address from the hostname policy database in block 212. The hostname policy database may have one or more records that contain a secure DNS server address that corresponds to a hostname. In some embodiments, addresses for two or more secure DNS servers may be listed for a particular hostname. In such an embodiment, the client may attempt to connect to one of the secure DNS servers and, if the connection fails, may attempt to connect to another secure DNS server listed for the particular hostname. Such logic is not illustrated in embodiment 200.

After determining an address for a secure DNS server in block 212, a connection is made with the secure DNS server in block 214. In many embodiments, the connection in block 214 may be preliminary handshaking for the establishment of a secure connection.

In some embodiments, an address for a secure DNS server may be resolved from a hostname or other identifier. The hostname may be located in the database in block 212 and resolved using a query to a DNS server, such as a public DNS server, and the connection established in block 214 with the address received from the public DNS query.

The client may transmit an identifier or other authentication to the secure DNS server in block 216. In some embodiments, a client may send two or more different items that may serve as an identifier.

When a client establishes a connection with a secure DNS server in block 214, the client may transmit a network address such as an IP address in the initial communication. In some embodiments, a secure DNS server may check that network address against a list of permitted network addresses to determine if the client is permitted communication with the secure DNS server. In such embodiments, the network address may serve as one form of authentication for a client device.

Some embodiments may establish a communication session and perform additional authentication in block 216. For example, a client device may transmit a hardware related identifier, such as a Media Access Control (MAC) address, a serial number attached to a processor or other hardware, an identifier stored in an access card or dongle, or some other identifier associated with a client hardware device. In another example, a client device may transmit a user related identifier, such as a username, password, results from a fingerprint reader, or some other identifier.

A secure DNS server may use an identifier to authenticate the client. In some embodiments, the client may be authenticated so that the secure DNS server can verify that the client has permission to access the host associated with the requested network address.

A secure connection may be established between the client and secure DNS server in block 218. In some embodiments, authentication of the client to the secure DNS server may occur before or after a secure connection is established.

A secure connection may be established using any type of security mechanism. In some cases, a Layer 3 protocol such as IPsec may be used to establish a secure session. In other cases, higher layer protocols such as SSL may be used. In some embodiments, a secure connection may include mutual authentication and may also include encryption of messages passed between the devices. A secure connection may thwart various malicious attacks where communications are intercepted and changed between a client and a secure DNS server.

Once a secure connection is established, a query may be transmitted by a client in block 220 and a hostname address returned in block 222. The secure connection may be torn down in block 224.

The client may establish a connection with the desired host using the hostname address in block 226 and may establish a secure connection with the host in block 228.

In many embodiments, an error handling procedure may be included in a client method for communicating with a secure DNS server. For example, if a connection to a secure DNS server is not successful, the client may prevent an unsecure DNS query from being performed. In another example, if a failure occurs when attempting to connect with a first secure DNS server, a second secure DNS server may be attempted when two or more secure DNS servers are provided in the hostname policy database.

FIG. 3 is a flowchart illustration of an embodiment 300 showing a method for a secure DNS server. The embodiment 300 illustrates a simplified example of actions performed by a secure DNS server when communicating with a client that requests a network address for a hostname. Embodiment 300 may correspond with the operations of a secure name resolver 115 as illustrated in FIG. 1. Other embodiments may use different terminology or nomenclature and may include additional steps or may combine two or more steps into a single step. In other embodiments, some steps illustrated as serial may be performed in parallel and vice versa.

A connection request may be received in block 302. In many cases, a communication request may include a network address for a requesting client. The requester address may be looked up in a client database in block 304. If the requester is not in the client database in block 306, the request for communication may be ignored in block 308.

Some embodiments may not use a network address for an initial determination of whether or not to accept a request for communication. In some cases, such as a secure DNS server used by employees to access a corporation's private access points, employees may connect to the Internet and be provided network addresses from coffee shops, hotels, or other access points, making the network address a poor authenticator of the requestor in such situations.

A connection may be established in block 310 with the client. A secure connection may be established in block 312. In some cases, a secure connection may be established in a single step, while in other cases, an unsecure connection may be established first before a series of authentication and handshaking steps may be performed before a secure version of the connection is established.

The secure connection may use several different technologies, including IPsec, various encryption technologies, SSL, or other secure technologies.

The secure DNS server may request authentication in block 314 and receive authentication in block 316. If the authentication is not valid in block 318, the session may be terminated in block 320. In some cases, an error message or other communication may be sent in addition to terminating the session in block 320.

If the authentication is valid in block 318, the secure DNS server may transmit authentication to the client device in block 322. Such authentication may be in the form of an encryption device or code that may be used to decode transmissions. In other embodiments, the authentication may be an identifier that may be used by the client device to compare to a predefined identifier to verify the authenticity of the secure DNS server.

After the authentication and security measures are complete, the hostname address may be transmitted in block 324 and the connection may be torn down in block 326.

The foregoing description of the subject matter has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the subject matter to the precise form disclosed, and other modifications and variations may be possible in light of the above teachings. The embodiment was chosen and described in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and various modifications as are suited to the particular use contemplated. It is intended that the appended claims be construed to include other alternative embodiments except insofar as limited by the prior art. 

1. A method comprising: receiving a first request for a first network address for a first device having a first name; looking up said first name in a database; finding a first entry in said database, said first entry comprising said first name and an identifier associated with a secure DNS server; establishing an authenticated session with said secure DNS server using said identifier; querying said secure DNS server with a query comprising said first name; receiving said first network address; and establishing a connection with said first network address.
 2. The method of claim 1, said identifier associated with said secure DNS server being a second network address.
 3. The method of claim 2 further comprising: receiving a second request for a third network address for a second device having a second name; looking up said second name in said database; and not finding said second name in said database and performing a DNS query with an unsecured DNS server to determine said third network address.
 4. The method of claim 2 further comprising: receiving said first request for said first network address for said first device having a first name; looking up said first name in said database; finding said first entry in said database, said first entry comprising said first name and a second network address associated with a secure DNS server; attempting to establish an authenticated session with said secure DNS server using said second network address; failing to establish said authenticated session; and terminating further DNS queries comprising said first name using an unsecure DNS server.
 5. The method of claim 2, said authenticated session comprising a Layer 3 security mechanism.
 6. The method of claim 5, said Layer 3 security mechanism comprising IPsec.
 7. The method of claim 2, said authenticated session comprising transmitting a unique identifier to said secure DNS server.
 8. The method of claim 7, said unique identifier being an identifier for a device.
 9. The method of claim 7, said unique identifier being an identifier for a user.
 10. A client device comprising: a database comprising at least one secure DNS server address and at least one host name to be resolved by said at least one secure DNS server; a secure name resolver adapted to: receive a first request for a first network address for a first device having a first name; look up said first name in a database; find a first entry in said database, said first entry comprising said first name and a second network address associated with a secure DNS server; establish an authenticated session with said secure DNS server using said second network address; query said secure DNS server with a query comprising said first name; receive said first network address; a unsecured name resolver.
 11. The client device of claim 10, said secure name resolver further adapted to: receive a second request for a third network address for a second device having a second name; look up said second name in said database; and not finding said second name in said database and performing a DNS query with said unsecured name resolver.
 12. The client device of claim 10, said secure name resolver further adapted to: receive said first request for said first network address for said first device having a first name; look up said first name in said database; find said first entry in said database, said first entry comprising said first name and a second network address associated with a secure DNS server; attempt to establish an authenticated session with said secure DNS server using said second network address; fail to establish said authenticated session; and terminate further DNS queries comprising said first name using said unsecure name resolver.
 13. The client device of claim 10, said authenticated session comprising a Layer 3 security mechanism.
 14. The client device of claim 13, said Layer 3 security mechanism comprising IPsec.
 15. The client device of claim 7 further comprising: a unique identifier, said unique identifier being transferred to said secure DNS server as part of said authenticated session.
 16. A secure name resolver comprising: a security mechanism adapted to establish a secure connection; a first database comprising at least one client device identifier; a second database comprising at least one network address and at least one network name; and a secured name resolver adapted to: authenticate a first client device; establish said secure connection with said first client device; and process a request for said at least one network address, said request comprising a network name.
 17. The secure name resolver of claim 16, said secured name resolver further adapted to: refuse to communicate with a second client device, said second client device being not found in said first database.
 18. The secure name resolver of claim 16, said security mechanism comprising a Layer 3 security mechanism.
 19. The secure name resolver of claim 18, said Layer 3 security mechanism comprising IPsec.
 20. The secure name resolver of claim 16, said authenticate comprising receiving a unique identifier for said client device. 